Celestial scheduling of a smart streetlight controller

ABSTRACT

A method to control a streetlight with a smart streetlight controller, includes isolating a terrestrial position of the smart streetlight controller, isolating a specific date, and calculating, at the smart streetlight controller, a time value associated with an event, such as sunrise or sunset, that is defined by a position of the sun on the specific date. The method further includes generating a streetlight control time by applying an offset to the time value, and executing a streetlight control command, such as a command to turn the streetlight on or off, at the streetlight control time.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the priority benefit of U.S. Provisional PatentApplication No. 63/002,190, filed Mar. 30, 2020. This application ishereby incorporated by reference in its entirety.

BACKGROUND Technical Field

The present disclosure generally relates to a programmatic scheduling ofturn-on and turn-off times for streetlight controllers. Moreparticularly, but not exclusively, the present disclosure relates tocontrolling a streetlight based on a calculated position of the sunrelative to a specific terrestrial location.

Description of the Related Art

Known streetlight controllers have onboard photo-sensitive circuitrythat is arranged to generate one or more outputs based on sensed lightin the area proximate the photo-sensitive circuitry. Simply, when thephoto-sensitive circuitry of the streetlight controller detects thatambient light has fallen below a threshold, the streetlight turns on,and when the circuitry detects that ambient light has risen above athreshold, the streetlight turns off.

All of the subject matter discussed in the Background section is notnecessarily prior art and should not be assumed to be prior art merelyas a result of its discussion in the Background section. Along theselines, any recognition of problems in the prior art discussed in theBackground section or associated with such subject matter should not betreated as prior art unless expressly stated to be prior art. Instead,the discussion of any subject matter in the Background section should betreated as part of the inventor's approach to the particular problem,which, in and of itself, may also be inventive.

BRIEF SUMMARY

The following is a summary of the present disclosure to provide anintroductory understanding of some features and context. This summary isnot intended to identify key or critical elements of the presentdisclosure or to delineate the scope of the disclosure. This summarypresents certain concepts of the present disclosure in a simplified formas a prelude to the more detailed description that is later presented.

The device, method, and system embodiments described in this disclosure(i.e., the teachings of this disclosure) enable a smart streetlightcontroller to identify its own terrestrial location, calculate theposition and orientation of the sun relative to that terrestriallocation on Earth, determine sunrise and sunset times at the smartstreetlight controller location, and control the light sourceaccordingly. The inventor has further contemplated various adjustmentsto the control based on capabilities of the smart streetlightcontroller. For example, any suitable offset from the time a lightsource turns on or turns off may be applied. Exemplary and non-limitingoffsets may include manual adjustments, programmatic adjustments,adjustments for local weather conditions, adjustments for othercelestial events (e.g., full moon, eclipse, and the like), adjustmentsfor season, and adjustments for daylight savings time. Other adjustmentsbased on locally sensed circumstances and data available in one or moredatabases, repositories, websites, or other network-accessible sourcesare also contemplated.

In a first embodiment, a smart streetlight controller includes: astandardized powerline interface arranged to electromechanically couplethe smart streetlight controller to a streetlight, the standardizedpowerline interface having primary contacts arranged to pass a pluralityof power transmission signals and secondary contacts arranged tocommunicate illumination signal information to the streetlight when thesmart streetlight controller is installed at the streetlight; a locationpositioning device; a control interface arranged to communicateillumination signal information to a streetlight; a processor arrangedto receive terrestrial position information from the location positiondevice; and a memory coupled to the processor. The memory hasinstructions stored therein which, when executed by the processor, causethe processor to: isolate, via the terrestrial position information, aterrestrial position of the smart streetlight controller; isolate aspecific date; calculate a time value associated with an event definedby a position of the sun on the specific date at the terrestrialposition; generate a streetlight control time by applying an offset tothe time value; and cause the illumination signal information to bepresented to the at least one set of secondary contacts at thestreetlight control time. One example of a location positioning systemis a global positioning system (GPS) device.

In some cases of the first embodiment, the standardized powerlineinterface is compliant with a roadway area lighting standard promoted bya standards body. In some cases, the terrestrial position includes alatitude value and a longitude value. Sometimes, the illumination signalinformation directs the streetlight to turn on or the illuminationsignal information directs the streetlight to turn off. And sometimes,the illumination signal information directs the streetlight to dim to aspecific light output or the illumination signal information directs thestreetlight to flash. In these or other cases of the first embodiment,the specific date is derived from the terrestrial position information.

In a second embodiment, a non-transitory computer-readable storagemedium has stored contents that configure a smart streetlight controllerto perform a method. The method includes: isolating a terrestrialposition of the smart streetlight controller based on informationreceived from a location positioning module; isolating a specific date;based on a position of the sun on the specific date at the terrestrialposition, generating a streetlight control time; and causingillumination signal information to be presented to a set of secondarycontacts at the streetlight control time. The set of secondary contactsis integrated in a standardized powerline interface of the smartstreetlight controller, the standardized powerline interface is arrangedto electromechanically couple the smart streetlight controller to astreetlight via primary contacts, and the secondary contacts arearranged to communicate illumination signal information to thestreetlight when the smart streetlight controller is installed at thestreetlight. One example of a location positioning system is a globalpositioning system (GPS) device.

In some cases of the second embodiment, the information received fromthe location positioning module providing the terrestrial positionrepresents a latitude value and a longitude value of the smartstreetlight controller, and in some cases, the specific date is in acurrent date at a location where the smart streetlight controller isinstalled. Sometimes, the method further includes applying auser-controlled offset to the illumination signal information.

In a third embodiment, a method to control a streetlight with a smartstreetlight controller, includes: isolating a terrestrial position ofthe smart streetlight controller; isolating a specific date;calculating, at the smart streetlight controller, a time valueassociated with an event defined by a position of the sun relative tothe terrestrial position of the smart streetlight controller on thespecific date; generating a streetlight control time by applying anoffset to the time value; and executing a streetlight control command atthe streetlight control time.

In some cases of the third embodiment, the event is a local time ofsunrise at the terrestrial position, and in some cases, the event is alocal time of civil dawn at the terrestrial position. In these and othercases, the event is a local time of sunset at the terrestrial positionor a local time of civil dusk at the terrestrial position. Sometimes,the offset for sunset is different from the offset for sunrise. In atleast some cases of the third embodiment, the offset is zero or auser-controlled value. In some cases, the terrestrial position includesa latitude value and a longitude value, and in some cases, the specificdate is in a Gregorian calendar format.

This Brief Summary has been provided to describe certain concepts in asimplified form that are further described in more detail in theDetailed Description. The Brief Summary does not limit the scope of theclaimed subject matter, but rather the words of the claims themselvesdetermine the scope of the claimed subject matter.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments are described with referenceto the following drawings, wherein like labels refer to like partsthroughout the various views unless otherwise specified. The sizes andrelative positions of elements in the drawings are not necessarily drawnto scale. For example, the shapes of various elements are selected,enlarged, and positioned to improve drawing legibility. The particularshapes of the elements as drawn have been selected for ease ofrecognition in the drawings. One or more embodiments are describedhereinafter with reference to the accompanying drawings in which:

FIG. 1 is a system level deployment having a plurality IIOT deviceembodiments;

FIG. 2 is portion of a light pole and fixture with a smart sensor IIOTdevice;

FIG. 3A is a smart streetlight controller embodiment;

FIG. 3B is an embodiment of a base of the smart streetlight controllerof FIG. 3A;

FIG. 4A is a data flow diagram representing processing of an algorithmicmodule that calculates time values based on a calculated position of thesun relative to a specific terrestrial position on Earth; and

FIG. 4B is a data flow diagram representing processing of a smartstreetlight controller to generate one or more streetlight controltimes.

DETAILED DESCRIPTION

The present disclosure may be understood more readily by reference tothis detailed description and the accompanying figures. The terminologyused herein is for the purpose of describing specific embodiments onlyand is not limiting to the claims unless a court or accepted body ofcompetent jurisdiction determines that such terminology is limiting.Unless specifically defined herein, the terminology used herein is to begiven its traditional meaning as known in the relevant art.

In the following description, certain specific details are set forth inorder to provide a thorough understanding of various disclosedembodiments. However, one skilled in the relevant art will recognizethat embodiments may be practiced without one or more of these specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures associated with computing systemsincluding client and server computing systems, as well as networks havenot been shown or described in detail to avoid unnecessarily obscuringdescriptions of the embodiments.

Smart streetlight controllers of the type described herein may also bereferred to as Internet of Things (IOT) devices or Industrial Internetof Things (IIOT) devices. IOT and IIOT devices are fixed and/or mobileelectronic computing devices that are coupled or coupleable to acomputing network. IOT devices are often described as devices withconsumer facing applicability and IIOT devices are often described asdevices with industrial, or machine-to-machine, applicability. The twotypes of devices (i.e., IOT and IIOT devices), and other like devices,have one or more computing processors, memory storing instructions thatdirect operations of the one or more computing processors, and networkcircuitry. In many cases, the IOT and IIOT devices also include a powersource (e.g., one or more of a battery, a physical power interface, apower supply, a photovoltaic cell, an induction coil, etc.), at leastone sensor (e.g., accelerometer, thermometer, pressure sensor, etc.),and memory to store data collected by the device, control parameters, orboth.

To avoid confusing or obfuscating the inventive subject matter disclosedherein, the present disclosure will predominantly describe system,method, and device embodiments in the context of one or more smartstreetlight controllers or IIOT devices. Nevertheless, one of skill inthe art will recognize that the principles described herein are not solimited, and such principles may be equally applicable to IOT devices,specialized computing devices, other smart devices, smart home devices,mobile computing devices, wearable devices, and other like devices.Accordingly, unless expressly described otherwise, or unless the contextdemands otherwise, each use of the term “IIOT” may be interchangeablyreplaced with the terms, “IOT,” “smart,” or any other suitable term.

Rather than a general-purpose computing device, an IIOT device istypically arranged to perform a particular function or set of functionssuch as controlling a streetlight. In other cases, an IIOT device may,for example, be arranged as an environmental sensor that collects datasuch as temperature, humidity, air quality, and the like. In thesecases, the IIOT device is deployed in a city, rural area, or some otherlocation, and the device is either programmed on site or at the factoryto communicate with a specific local or remote computing server. Thelocal or remote computing server may be arranged at a great distance(e.g., tens, hundreds, or even thousands of miles away) from the IIOTdevice. Alternatively, the local or remote computing server may be asmart phone tablet, or other computing device permanently ortransitorily arranged a short distance (e.g., tens or hundreds of feetor inches or some other distance) from the IIOT device. In these cases,the IIOT device is programmed to communicate data to, from, or to andfrom a specific local or remote computing server.

The smart streetlight controllers illustrated in the present figures anddescribed in the present specification improve the reliability, energyefficiency, and safety of streetlighting. Conventional streetlightcontrollers include photo-sensitive circuitry (e.g., a photosensor) todetermine when the streetlight should turn on and when the streetlightshould turn off. If the photosensor circuit fails, or if a window to thesensor is obstructed (e.g., by dirt, fowl, damage, or some other cause),the streetlight may either be wastefully over-illuminated (e.g., alwaysilluminated) or dangerously under-illuminated (e.g., alwaysextinguished). In the present disclosure, a programmatic approach toovercome the limitations of conventional streetlight controllers isproposed. The new approach may be used cooperatively withphoto-sensitive circuitry or as an alternative to photo-sensitivecircuitry. What's more, with a determined level of expected ambientlight, the streetlight controller may finely tune a streetlight toilluminate more brightly or less brightly in a desired way (e.g., morebrightly in a new moon cycle, less brightly in a full moon cycle, morebrightly in the middle of the night, less brightly at dawn and dusk, andthe like). This improvement can increase safety, save energy, andprovide a more uniform illumination over the course of a single eveningor a climatic season. The device, method, and system embodimentsdescribed in this disclosure (i.e., the teachings of this disclosure)enable a smart streetlight controller to identify its own terrestriallocation (i.e., a substantially exact location on Earth where thestreetlight is positioned), calculate the position and orientation ofthe sun relative to that terrestrial location on Earth, determinesunrise and sunset times at the terrestrial location of the smartstreetlight controller, and control the light source accordingly. It hasbeen further contemplated that various adjustments to the streetlightcontrol can be made based on certain capabilities of the smartstreetlight controller. For example, a user may direct a suitable offsetbe applied to the calculated time that a light source should orotherwise does turn on or turn off. Other exemplary and non-limitingoffsets may include manual adjustments, programmatic adjustments,adjustments for local weather conditions, adjustments for othercelestial events (e.g., full moon, eclipse, and the like), adjustmentsfor season, and adjustments for daylight savings time. And still otheradjustments based on locally sensed circumstances and data available inone or more databases, repositories, websites, or othernetwork-accessible sources are also contemplated.

Smart streetlight controllers are generally coupled to a streetlightluminaire via a standardized powerline interface. The standardizedpowerline interface defines a limited number of electrical/communicativeconduits over which signals may be passed in-to or out-from thestreetlight controller. In some cases, as will be discussed herein, theinterface may be referred to as a Zhaga interface, a NEMA interface, aNEMA socket, an ANSI C136 interface, or the like. In some embodiments,this interface includes primary contacts arranged to pass a plurality ofpower transmission signals and secondary contacts arranged tocommunicate illumination signal information to the streetlight when thesmart streetlight controller is installed at the streetlight. Thesecondary contact may also be referred to as a control interface, adimming interface, or some other like term.

A known NEMA interface implements the powerline interface withconnectors and receptacles that include seven electrical/communicativeconduits (e.g., pins, blades, springs, connectors, receptacles, sockets,and other like “contacts”). A set of three primary contacts carry a Linevoltage signal, a Load voltage signal, and Neutral voltage signal. A setof four secondary contacts may be used by the streetlight controller topass power, control information, status information, and the like. Thefour secondary contacts may be treated as a first pair of secondarycontacts and a second pair of secondary contacts.

FIG. 1 is a system level deployment 100 having a plurality of IIOTdevice embodiments. At least one IIOT device is implemented as a smallcell networking device and a plurality of IIOT devices are implementedas smart sensor devices coupled to streetlight fixtures. The smartsensor devices are in many, but not all, cases implemented as smartstreetlight controllers. The plurality of smart sensor devices includesthe inventive celestial scheduling technology described in the presentdisclosure. The small cell networking device, traffic lights, publicinformation signs, private entity signs, and the like may also includecelestial scheduling technology of the type described here.

The sun and moon 101 are shown in FIG. 1 . Light or the absence of lightbased on time of day, weather, geography, or other causes provideinformation (e.g., ambient light) to light sensors of light pole mounteddevices described in the present disclosure. Additionally, oralternatively, light or the absence of light may be calculated based onthe celestial positions of the sun, moon, and stars relative to theterrestrial position (i.e., geographic location) of a streetlight ofinterest relative. Based on this electronically captured orprogrammatically derived information, an associated light source may besuitably controlled.

Streetlight fixtures in FIG. 1 are coupled to, or otherwise arranged aspart of, a system of streetlight poles, and each streetlight fixtureincludes a light source. Each light source, light fixture, and lightfitting, individually or along with their related components, may insome cases be interchangeably referred to as a luminaire, a lightsource, a streetlight, a streetlamp, or some other such suitable term.In the system level deployment 100, at least one light pole includes afixture with a small cell networking device 102, and a plurality oflight poles each have a smart sensor IIOT device 104A-104H. In thepresent disclosure, light poles having a smart sensor IIOT device104A-104H may individually or collectively be referred to as light poleshaving a smart sensor IIOT device 104 or simply light poles 104 forbrevity. In these cases, and for the purposes of the present disclosure,the light sensor of each light pole 104 may be structurally andoperatively identical (i.e., having same or substantially similarcircuitry and embedded software, and differing by way of one or morenetwork-level system identifiers).

As shown in the system level deployment 100, a plurality of light poles102, 104 are arranged in one or more determined geographic areas, andeach light pole 102, 104 has at least one light source positioned in afixture. The fixture is at least twenty feet above ground level and inat least some cases, the fixtures are between about 20 feet and 40 feetabove ground level. In other cases, the streetlight fixtures may ofcourse be lower than 20 feet above the ground or higher than 40 feetabove the ground. In other system level deployments according to thepresent disclosure, there may be 1,000 or more light poles 102, 104arranged in one or more determined geographic areas. In these or instill other cases, the streetlight fixtures may of course be lower than20 feet above the ground or higher than 40 feet above the ground.Although described as being above the ground, streetlight fixtures shownand contemplated in the present disclosure may also be subterranean, butpositioned above the floor, such as in a tunnel.

The system of streetlight poles, streetlight fixtures, streetlightsources, or the like in the system level deployment may be controlled bya municipality or other government agency. In other cases, the systemstreetlight poles, streetlight fixtures, streetlight sources, or thelike in the system level deployment is controlled by a private entity(e.g., private property owner, third-party service contractor, or thelike). In still other cases, a plurality of entities shares control ofthe system of streetlight poles, streetlight fixtures, streetlightsources, or the like. The shared control may be hierarchical orcooperative in some other fashion. For example, when the system iscontrolled by a municipality or a department of transportation, anemergency services agency (e.g., law enforcement, medical services, fireservices) may be able to request or otherwise take control of thesystem. In still other cases, one or more sub-parts of the system ofstreetlight poles, streetlight fixtures, streetlight sources, or thelike can be granted some control such as in a neighborhood, around ahospital or fire department, in a construction area, or in some othermanner.

In the system level deployment 100 of FIG. 1 , any number of streetlightpoles 102, 104 and their associated fixtures may be arranged with aconnector that is compliant with a roadway area lighting standardpromoted by a standards body such as ANSI C136.41 (e.g., a NEMA-basedconnector/socket system). The connector permits the controlling orservicing authority of the system to competitively and efficientlypurchase and install light sensors on each streetlight fixture. Inaddition, or in the alternative, the standardized connector in eachstreetlight fixture permits the controlling or servicing authority toreplace conventional light sensors with other devices such as a smallcell networking device, a smart sensor IIOT device embodied as a smartstreetlight controller 120 (FIGS. 2-3 ), or some other IIOT device.

In the system level deployment 100, a small cell networking device iselectromechanically coupled to a selected light pole 102 wherein theelectromechanical coupling is performed via the connector that iscompliant with the roadway area lighting standard promoted by astandards body. Stated differently, the system level deployment 100includes at least one light pole and fixture with a small cellnetworking device 102, and a plurality of light poles each having asmart sensor IIOT device 104A-104H. In these light poles 104, eachstreetlight fixture is equipped with a standalone IIOT device, such asthe smart streetlight controller 120 of FIGS. 2, 3 , that iselectromechanically coupled via a respective connector compliant withthe roadway area lighting standard promoted by the standards body. Inthis arrangement, each streetlight 102, 104 is equipped with a lightsensor circuit that is further electrically coupled to a processor-basedlight control circuit. In at least some of these embodiments,electrically coupling the light sensor to the processor-based lightcontrol circuit includes passing a signal representing an amount oflight detected by the light sensor to the processor-based light controlcircuit. In at least some of these embodiments, the light sensor isarranged to detect an amount of lux, lumens, or other measurement ofluminous flux and generate the signal representing the amount of lightdetected.

The processor-based light control circuit of each IIOT device (e.g.,each smart streetlight controller 120) is arranged to provide a lightcontrol signal to the respective light source based on at least oneambient light signal generated by a light sensor associated with theprocessor-based light control circuit. In addition, because eachstreetlight 102, 104 is equipped with communication capabilities, eachlight source in each streetlight 102, 104 can be controlled remotely asan independent light source or in combination with other light sources.In at least some of these cases, each of the plurality of light polesand fixtures with a smart sensor IIOT device 104 is communicativelycoupled to the light pole and fixture with a small cell networkingdevice 102. The communicative relationship from each of the plurality oflight poles and fixtures with a smart sensor IIOT device 104 to thelight pole and fixture with a small cell networking device 102 may be adirect communication or an indirect communication. That is, in somecases, one of the plurality of light poles and fixtures with a smartsensor IIOT device 104 may communicate directly to the light pole andfixture with a small cell networking device 102 or the one of theplurality of light poles and fixtures with a smart sensor IIOT device104 may communicate via one or more other ones of the plurality of lightpoles and fixtures with a smart sensor IIOT device 104 or via some othermeans (e.g., via a cellular communication to a traditional cellularmacro-cell, via a wired connection, or the like).

In the system level deployment 100 of FIG. 1 , various ones of the lightpoles may be 50 feet apart, 100 feet apart, 250 feet apart, or someother distance. In some cases, the type and performance characteristicsof each small cell networking device and each smart sensor IIOT device(e.g., smart streetlight controller 120) are selected based on theirrespective distance to other such devices such that wirelesscommunications are acceptable.

The light pole and fixture with a small cell networking device 102 andeach light pole and fixture with a smart sensor IIOT device 104 may bedirectly or indirectly coupled to a street cabinet 108 or other likestructure that provides utility power (e.g., “the power grid”) in awired way. The utility power may provide 120 VAC, 208 VAC, 220 VAC, 240VAC, 260 VAC, 277 VAC, 360 VAC, 415 VAC, 480 VAC, 600 VAC, or some otherpower source voltage. In addition, the light pole and fixture with asmall cell networking device 102, and optionally one or more of thelight poles and fixtures with smart sensor devices 104A-104H, are alsocoupled to the same street cabinet 108 or another structure via a wiredbackhaul connection. It is understood that these wired connections arein some cases separate wired connections (e.g., copper wire, fiber opticcable, industrial Ethernet cable, or the like) and in some casescombined wired connections (e.g., power over Ethernet (PoE), powerlinecommunications (PLC), or the like). For simplification of the systemlevel deployment 100 of FIG. 1 , the wired backhaul and power line 106is illustrated as a single line. In the embodiment of FIG. 1 , thestreet cabinet 108 is coupled to the power grid, which is administeredby a licensed power utility agency, and the street cabinet 108 iscoupled to the public switched telephone network (PSTN). In otherembodiments, the street cabinet 108 may be electrically,communicatively, or electrically and communicatively to some otherinfrastructure (e.g., power source, satellite communication network, orthe like) such as a windmill, generator, solar source, fuel cell,satellite dish, long- or short-wave transceiver, or the like.

In some embodiments, any number of small cell networking devices 102 andsmart sensor devices 104 are arranged to provide utility grade powermetering functions. The utility grade power metering functions may beperformed with a circuit arranged apply any one or more of a full load,a partial load, and a load where voltage and current are out of phase(e.g., 60 degrees; 0.5 power factor). Other metering methodologies arealso contemplated.

Each light pole and fixture with a smart sensor IIOT device 104 is indirect or indirect wireless communication with the light pole andfixture that has the small cell networking device 102. In addition, eachlight pole and fixture with a smart sensor IIOT device 104 and the lightpole and fixture with the small cell networking device 102 may also bein direct or indirect wireless communication 112 with an optional remotecomputing device 110. The remote computing device 110, when it isincluded in the system level deployment 100, may be controlled by amobile network operator (MNO), a municipality, another governmentagency, a third party, or some other entity. By this optionalarrangement, the remote computing device 110 can be arranged towirelessly communicate light control signals and any other information(e.g., packetized data) between itself and each respective wirelessnetworking device coupled to any of the plurality of light poles. A user114 holding a mobile device 116 is represented in the system leveldeployment 100 of FIG. 1 . A vehicle having an in-vehicle mobile device118 is also represented. The vehicle may be an emergency servicevehicle, a passenger vehicle, a commercial vehicle, a publictransportation vehicle, a drone, or some other type of vehicle. The user114 may use their mobile device 116 to establish a wirelesscommunication session over a cellular-based network controlled by anMNO, wherein packetized wireless data is passed through the light poleand fixture with a small cell networking device 102. Concurrently, thein-vehicle mobile device 118 may also establish a wireless communicationsession over the same or a different cellular-based network controlledby the same or a different MNO, wherein packetized wireless data of thesecond session is also passed through the light pole and fixture with asmall cell networking device 102.

Other devices may also communicate through light pole-based devices ofthe system level deployment 100. These devices may be IOT devices, IIOTdevices, or some other types of smart devices. In FIG. 1 , two publicinformation signs 120A, 120B, and a private entity sign 120C are shown,but many other types of devices are contemplated. Each one of thesedevices may form an unlicensed wireless communication session (e.g.,WiFi) or a cellular-based wireless communication session with one ormore wireless networks made available by the devices shown in the systemlevel deployment 100 of FIG. 1 . FIG. 2 is portion of a streetlight poleand luminaire fixture with a smart sensor IIOT device 104. A streetlightsupport structure 136 (e.g., a pole) supports the luminaire 138. Theluminaire 138 has a top-side connector (e.g., a socket) that iscompliant with a roadway area lighting standard promoted by a standardsbody such as ANSI C136.41 (e.g., a NEMA-based connector/socket system).A smart sensor IIOT device arranged as a smart streetlight controller120 includes a corresponding connector (e.g., a set of “pins”) at itsbase, which permits electro-mechanical coupling of the smart sensor IIOTdevice (e.g., smart streetlight controller 120) to the luminaire 138.

The smart sensor IIOT device in FIG. 2 is configured as a smartstreetlight controller 120. The smart streetlight controller 120 hassupport circuitry including a power supply, a controller arranged todirect a volume of light 140 output from the luminaire 138 associatedwith the smart streetlight controller 120 (e.g., a pulse widthmodulation (PWM) controller, a light emitting diode (LED) driver,dimming circuit, ballast, and the like), and certain switching andcontrol circuits, which are further described in the present disclosure.

In some cases, the smart streetlight controller 120 is configured tocapture data regarding any type of condition to be sensed 244 inproximity of the streetlight or streetlight pole where the smartstreetlight controller 120 is deployed. Based on any such condition, thevolume of light 140 may be adjusted. In at least some cases, the smartstreetlight controller 120 is configured to report any number of sensedconditions to a customer-based computing server. In these cases, thecustomer-based computing server may collect information about thestreetlight, the area proximal to the streetlight, the status of theluminaire 138, the status of the light source, or any other data.

The smart streetlight controller 120 may also optionally includephoto-sensitive circuitry that senses ambient light from the sun/moon101. The smart streetlight controller 120 may use the sensed informationto control the volume of light 140 from the luminaire 138. Additionally,as described herein, the smart streetlight controller 120 includescomputational circuitry to calculate certain time information (e.g.,sunrise and sunset) based on the terrestrial location of the smartstreetlight controller 120 and celestial movement of the sun relative tothe location of the smart streetlight controller 120 on Earth. Using thecalculated sunrise and sunset information, and optionally using on otherinformation and input, the smart streetlight controller 120 may furthercontrol the light output from the luminaire 138.

FIG. 3A is a smart streetlight controller 120 embodiment. FIG. 3B is anembodiment of a base 128 of the smart streetlight controller 120 of FIG.3A. The base 128 conforms to a standardized powerline interface. In thepresent disclosure, FIGS. 3A-3B may be individually or collectivelyreferred to as FIG. 3 . Structures earlier identified are not repeatedfor brevity.

The smart streetlight controller 120 is arranged with a generallycylindrical housing 122. The generally cylindrical housing 122 may beformed of a plastic, a glass, a metal, a composite material, or anyother suitable material. The generally cylindrical housing 122 may insome cases have heat dissipation properties to assist in the removal ofheat generated by electronic circuitry inside the housing. In at leastsome cases, the generally cylindrical housing 122 is arranged to resistnesting birds or other animals. In at least some cases, the generallycylindrical housing 122 is arranged to resist an accumulation of dirt,snow, or any foreign bodies or materials. In at least some cases, thegenerally cylindrical housing 122 is symmetrically arranged to have agenerally same visual appearance when viewed from any perspective.

The generally cylindrical housing 122 includes a connector 124 (e.g., aset of “pins”) that is compliant with a standardized powerlineinterface. In the embodiment of FIG. 3 , the standardized powerlineinterface is a roadway area lighting standard promoted by a standardsbody such as ANSI C136.41 (e.g., a NEMA-based connector/socket system),but other standardized powerline interfaces are contemplated (e.g., aninterface compliant with the ZHAGA CONSORTIUM, which is an internationalassociation that creates industry standards in the LED lightingindustry). When the smart streetlight controller 120 is deployed, thepins of the connector 124 mate with a corresponding receptacle (e.g., asocket) that is integrated in a streetlight, a luminaire, a control box,or some other structure, which permits electro-mechanical coupling ofthe smart streetlight controller 120 to the streetlight, luminaire,control box, or the like.

The generally cylindrical housing 122 of the smart streetlightcontroller 120 includes a light-transmissive surface 126. The lighttransmissive surface may be transparent or partially transparent (e.g.,partially opaque). In some embodiments, the light-transmissive surface126 is integrated with the generally cylindrical housing 122, and inother cases, the light-transmissive surface 126 is a distinct structurethat is removably or fixedly coupled to the generally cylindricalhousing 122. In the embodiment of FIG. 3 , the light-transmissivesurface 126 is arranged at a “top” of the smart streetlight controller120, but in at least some embodiments, the light-transmissive surface126 is formed additionally or alternatively in or through a surface wallof the generally cylindrical housing 122. Generally, thelight-transmissive surface 126 permits ambient light to reach anelectronic light sensor (e.g., a photosensor, which is not shown in FIG.3 ) formed within a volumetric cavity inside the generally cylindricalhousing 122. As described in the present disclosure, the light sensor isarranged, in at least some cases, to provide a first output signal thatdirects a light source to illuminate when light reaching the lightsensor crosses a determined first threshold, and to provide a secondsignal (e.g., an alteration of the first signal or a different signal)when the light reaching the light sensor crosses a determined secondthreshold. In some cases, the first and second thresholds are the samethresholds, and in some cases, the first and second thresholds aredifferent thresholds.

One of skill in the art will recognize that the smart streetlightcontroller 120 embodiment of FIG. 3A is non-limiting. In other cases,rather than a streetlight controller, or rather than a streetlightcontroller in the generally cylindrical housing 122, the device of FIG.3A may be realized as any suitable smart sensor IIOT device and in anysuitable housing shape, form, configuration, and the like.

The smart streetlight controller 120 depicted in FIG. 3A, and in factthe smart devices contemplated in the present disclosure, are understoodby those of skill in the art to apply to many types of smart devicesincluding small cells, smart hubs, smart streetlight controllers, smartmonitor devices, and many others. The embodiment of FIG. 3A includes amicrocontroller 160. The smart streetlight controller 120 also includesa standardized powerline interface 124, which in the embodiment of FIG.3A is along the lines of, but not limited to, a NEMA-based connector.

The microcontroller 160 is arranged with a processor 162, acommunications module 164, an input/output (I/O) module 166, resetcircuitry 168, a location/identification module 170 (e.g., globalpositioning system (GPS), a WiFi, Bluetooth, LAN, mobile towertriangulation location signals, local government or mobile locationdevice, MAC ID, IMEI module, or some other unique location oridentification device), and certain other circuits 172. In someembodiments, the location/identification module 170 will have a memoryand be able to store the location information that it receives from anysource, including any of the above stated or from a local transfer atthe time of installation. In some embodiments, thelocation/identification module will be installed at fixed location, suchas street light on a light pole and will not move after installation.The location might be uploaded from another circuit that has storedtherein the location of that light pole, such as a local memory, a wiredinput, a wireless input or other source, such as those listed elsewhereherein. Additionally, the microcontroller 140 may optionally include apulse width modulation (PWM) circuit 174, a digital addressable lightinginterface (DALI) controller 176, and a DALI power supply 178. Themicrocontroller 140 is represented with a dashed line box to make clearthat in some cases, the various circuits and modules are included in asingle microcontroller package, and in other cases, any one or more ofthe modules 162-178 may be partially included in a microcontrollerpackage and partially outside a microcontroller package, or any one ormore of the modules 162-178 may be entirely outside of themicrocontroller package. Additionally, any one or more of the modules162-178 may be optionally included or excluded. The particulardescription herein with respect to the smart streetlight controller 120of FIG. 3A does not divert from the teaching of the present disclosure,and any particular representation herein is not limiting unlessexpressly limited in the claims that follow.

In addition to the microcontroller 160, the smart streetlight controller120 also includes memory 180. The memory may in some cases be includedin the microcontroller 160, in any particular module of themicrocontroller 160, or in a separate and distinct package. The memory180 includes storage space for executable software instructions, which,when executed by processor 162, cause the smart streetlight controller120 to perform any particular programmed acts. The memory 180 alsoincludes an area to store data that is captured, received, created,determined, or in any other way generated. Implementations of acommunications protocol 186 may be stored in the memory 180. Thecommunications protocol may be any suitable protocol. In at least oneembodiment, such as the embodiment of FIG. 3A, a suitable communicationsprotocol is a message queueing telemetry transport (MQTT) protocol.

Memory 180 includes storage for a system-wide unique identifier 188(SWUI). The SWUI 188 may be stored in clear text. The SWUI 188 may beencrypted, hashed, or obfuscated in some other way. In some cases, theSWUI 188 is generated, populated, or otherwise implemented incooperation with the communications module 164, thelocation/identification module 170, or some other electronic circuitry(e.g., module) of the smart streetlight controller 120.

As described herein, the SWUI 188 may be formed from one or more partsor whole of an international mobile subscriber identity (IMSI) code,mobile country code (MCC), mobile network code (MNC), mobile sequentialserial number (MSIN), electronic serial number (ESN), integrated circuitcard identifier (ICCID), international mobile equipment identifier(IMEI), mobile station ISDN number (MSISDN), MAC address, one-timerandom number generator, or some other extended unique identifier (EUI)information or combination thereof.

In the embodiment of FIG. 3A, the processor 162 is arranged to executesoftware instructions (i.e., code 182) stored in the memory 180. Theexecution of such code 182 may include retrieving particular data 184stored in the memory 180, and in at least some cases the cooperationbetween the executing software code 182 and the data 184 stored in thememory 180 causes the I/O module 166 to operate the PWM circuitry 174,the DALI controller 176, the DALI power supply 178, or any of the othercircuitry 172. In at least one example, executed code 182 is arranged todirect output of visual light from a corresponding luminaire inaccordance with a pulse width modulate (PWM) signal generated by the PWMmodule 174.

As described herein, the smart streetlight controller 120 is arranged tooperate semi-autonomously. The smart streetlight controller 120 maycommunicate status information, warning information, alerts, or anyother suitable information toward a customer-based computing server. Theinformation may be communicated on a schedule, at a request, or upon anevent. The information, once passed, may be used, for example, topopulate one or more web pages deliverable to a user via a web-basedmanagement tool. In order to perform such communication, the informationmay be passed to and from the smart streetlight controller 120 via thecommunications module 164.

In the embodiment of FIG. 3A, the communications module 164 may bearranged as a wireless connection device capable of communicating on anysuitable medium (e.g., radio frequency (RF), optical, audio, ultrasound,or some other part of the electromagnetic spectrum). In at least somecases, the communications module 164 is arranged for a communicationmedium that conforms to a cellular or cellular-based protocol (e.g., 4G,LTE, 5G, 6G, or the like).

Notwithstanding the discussion herein, one of skill in the art willrecognize that the DALI modules 176, 178 are optional and may beimplemented in a variety of ways without diverting from the teaching ofthe present disclosure.

Turning to FIG. 3B, a view looking down onto the base 128 of the smartstreetlight controller 120 is presented. Seven contact surfaces areshown in a configuration that complies with a standardized powerlineinterface. A physical marking, “N” and a corresponding arrow arephysically labeled on the base to guide an installer as to the properorientation of a base 128 when installed.

In the embodiment of FIG. 3 , the standardized powerline interface has aset of primary contacts arranged to carry a Line voltage signal, a Loadvoltage signal, and a Neutral voltage signal, each of which is locatedabout a central location in the base 128 (i.e., semi-circular contactstructures (e.g., pins, blades, connectors, or the like) physicallylabeled “Line,” “Load,” and “Neut.” on the connector represented in FIG.3B). The primary contacts are arranged to pass a plurality of powertransmission signals, which may be high voltage alternating currentsignals (AC) of 220 VAC, 280 VAC, 480 VAC, or some other voltage.

The standardized powerline interface further has a set of secondarycontacts, which includes a first pair of secondary contacts 130, 132(i.e., two offset spring steel contacts physically labeled “4” and “5,”respectively, on the connector represented in FIG. 3B) and a second pairof secondary contacts 134, 136 (i.e., two offset spring steel contactsphysically labeled “6” and “7,” respectively, on the connectorrepresented in FIG. 3B). In cases where the standardized powerlineinterface conforms to a NEMA-based protocol such as ANSI C136.41, thefirst and second pairs of secondary contacts may be referred to as NEMApins 4/5 and NEMA pins 6/7, respectively. In some cases, the set of isarranged to carry illumination signal information such as a plurality ofoptional dimmer control signals. In cases where the set of foursecondary contacts pass dimmer control signals, it is recognized thatfour dimmer control signals permit two independent dimmer controlchannels. In some cases, a single dimmer control signal is used as anode for a reference plane (e.g., an earth/chassis ground), and threeseparate dimmer control signals are implemented or implementable. Inother cases, at least some of the four secondary contacts are arrangedto communicate encoded binary data, and in still other cases, thesecondary contacts implement a particular communication protocol (e.g.,USB, I2C, SPI, or the like).

The position of the sun may be calculated relative to any terrestrialcoordinates on Earth. More specifically, the position of the sunrelative to a specific position on Earth (e.g., latitude and longitude)may be calculated for any specific date and for any specific time.

Additionally, or alternatively, a specific time on a specific date thatthe sun is at a specific position relative to a specific earthlylocation can be calculated. This calculated value may be used asstreetlight control time. In this way, if a streetlight is desirablyturned on or turned off every day when the sun is at a same specificposition relative to the streetlight, the specific time of day when thesun is in that relative position can be calculated for any specific dateand used as a streetlight control time.

A streetlight control time, as the term is used herein, is a specifictime that a light source is controlled by a smart streetlight controller120 via certain illumination signal information. A streetlight controltime may be a time that the smart streetlight controller 120 directs thelight source to turn on, turn off, dim, dim to a specific light output,flash, flash a code or an encoded message, change the properties ofgenerated light (e.g., color, intensity, warmth, and the like), orcontrol the streetlight in any other way. A streetlight control time maybe positive or negative.

In some cases, a plurality of streetlight control times may be generatedand applied. Different streetlight control times may be arranged todirect different actions of the light source. A plurality of streetlightcontrol times may be prioritized. Accordingly, the concept ofstreetlight control times are flexibly implemented, and theimplementation of many different types and functions of streetlightcontrol times is contemplated.

In at least one embodiment, a streetlight control time desirably directsa streetlight to turn off at, or soon after, sunrise when the sun is ata first specific position relative to the streetlight. In at least oneembodiment, a streetlight control time desirably directs a streetlightto turn on at, or soon before, sunset when the sun is at a secondspecific position relative to the streetlight. Using the terrestrialposition of the streetlight (e.g., as determined by alocation/identification module 170), a first streetlight control time inany given day when the sun is at the first specific position can becalculated, and a second streetlight control time in the given day whenthe sun is at the second specific position can be calculated. These twospecific streetlight control times (i.e., the first and secondstreetlight control times) can be used to turn off the streetlight inthe morning and to turn on the streetlight at night. Hence, it is alsorecognized that these streetlight control times will naturally change(i.e., be re-calculated to different values) as time passes due to themotion of Earth around the sun.

Considering the operations of a smart streetlight controller 120 astaught in the present disclosure, several terms are now discussed.

Within the context of the present disclosure, the term, “sunrise,” meansan instant near daybreak of any given day under ideal meteorologicalconditions and with standard refraction of the rays of the sun when theupper edge of the sun's perimeter is coincident with an ideal horizon.

Within the context of the present disclosure, the term, “sunset,” meansan instant near nightfall of any given day under ideal meteorologicalconditions and with standard refraction of the rays of the sun when theupper edge of the sun's perimeter is coincident with an ideal horizon.

One of skill in the art will recognize that due to atmosphericrefraction, light from the sun is bent, or refracted, as it entersEarth's atmosphere, and for this reason, apparent sunrise occurs shortlybefore the sun crosses above the ideal horizon and apparent sunsetoccurs shortly after the sun crosses the below the ideal horizon. Inlight of these effects, which may be further compounded by changes inair pressure, changes in relative humidity, and other metrologicalconditions, it is recognized that streetlight safety may be improved byturning the streetlight on at some point before the calculated time ofsunset, and turning the streetlight off at some point after thecalculated time of sunrise.

Within the context of the present disclosure, the term, “civil dawn,”means the instant near daybreak of any given day under idealmetrological conditions and with standard refraction of the rays of thesun when the center of the sun is at a depression angle of six degrees(6°) below an ideal horizon. In the absence of moonlight or artificiallighting, a large object will be sufficiently illuminated that theobject can be seen, but no detail is discernible.

Within the context of the present disclosure, the term, “civil dusk,”means the instant near nightfall of any given day under idealmetrological conditions and with standard refraction of the rays of thesun when the center of the sun is at a depression angle of six degrees(6°) below an ideal horizon. In the absence of moonlight or artificiallighting, a large object will be sufficiently illuminated that theobject can be seen, but no detail is discernible.

Within the context of the present disclosure, the term, “latitude,”means an angular measurement of north-south location on Earth's surface.To add context, latitude ranges: 1) from ninety degrees (90°) south atthe South Pole; 2) through zero degrees (0°) all along Earth's equator;3) to ninety degrees (90°) north at the North Pole. Conventionally,latitude is a positive value in Earth's northern hemisphere and anegative value in the southern hemisphere.

Within the context of the present disclosure, the term, “longitude,”means an angular measurement of east-west location on Earth's surface.To add context, longitude ranges from the Prime Meridian, which passesthrough Greenwich, England. With reference to a three-hundred-sixty(360°) circle, the international date line is accepted at plus or minusone-hundred-eighty degrees (+/−180°) longitude because 180° eastlongitude is the same meridian as 180° west longitude. Conventionally,east longitude is referred to as positive and west longitude is referredto as negative.

Within the context of the present disclosure, the term, “celestialsphere,” means an abstract sphere centered on Earth and having anarbitrarily large radius. Along the lines of an imaginary spherical“movie screen,” all celestial objects in the sky (e.g., all stars,planets, and other bodies in space) are conceptually projected upon theinner surface of the movie screen (i.e., celestial sphere). Coordinateson the celestial sphere are specified in degrees of declination andright ascension, which is roughly analogous to latitude and longitudecoordinates on Earth's surface.

Within the context of the present disclosure, the term, “rightascension,” is roughly analogous to longitude within a system such as acelestial sphere. Right ascension defines an angular offset from themeridian of the point on the celestial sphere at which the plane ofEarth's orbit crosses the plane of Earth's equator, moving from south tonorth (i.e., an angular offset from the meridian of the vernal equinox).

Within the context of the present disclosure, the term, “declination,”is roughly analogous to latitude within a system such as a celestialsphere. Declination measures an angular displacement north or south fromthe projection of Earth's equator on the celestial sphere to thelocation of a celestial body. Along these lines, “solar declination”within the context of the present disclosure means the declination ofthe sun. Solar declination varies from: 1) minus twenty-three andforty-four hundredths degrees (−23.44°) at winter solstice (northerhemisphere); 2) through zero degrees (0°) at the vernal equinox; 3) toplus twenty-three and forty-four hundredths degrees (+23.44°) at summersolstice. A variation in solar declination is an astronomicaldescription of the sun (in the northern hemisphere) heading south forthe winter.

Within the context of the present disclosure, the term, “azimuth,” meansa value measured clockwise from true north to the point on the horizondirectly below the object in a particular coordinate system for locatingspecific positions in the sky. Azimuth is measured clockwise from truenorth to the point on the horizon directly below the object. Forexample, if the azimuth of a constellation is thirty-five degrees (35°)from north, and the elevation is sixty degrees (60°), the object can beseen by looking northeast, about two-thirds of the way up from thehorizon. Because Earth rotates, azimuth and elevation numbers for starsand planets constantly change with time and with the point on Earth fromwhich the object is observed.

Within the context of the present disclosure, the term, “elevation,”means a value measured vertically from an azimuthal point the horizon upto the object in a particular coordinate system for locating specificpositions in the sky. Elevation is measured angularly from the ground.For example, if the azimuth of a constellation isone-hundred-thirty-five degrees (135°) from north, and the elevation isthirty degrees (30°), the object can be seen by looking southeast, aboutone-third of the way up from the horizon. Because Earth rotates, azimuthand elevation numbers for stars and planets constantly change with timeand with the point on Earth from which the object is observed.

Within the context of the present disclosure, the term, “zenith angle,”means an angular value measured from straight up (zenith) to a point inthe sky. Zenith angle can be used in a particular coordinate system forlocating specific positions in the sky with azimuth to indicate theposition of a star or other celestial body. Zenith angle is thecomplementary angle of the elevation (i.e., elevation=ninety degreesminus zenith (90°—zenith)). The cosine of the solar zenith angle is usedin at least some cases to calculate the vertical component of directsunlight shining on a horizontal surface.

Within the context of the present disclosure, the term, “UTC,” meansCoordinated Universal Time. UTC is based on atomic clock time. Leapseconds are added when necessary to match earth-motion time. A UTCoffset is a difference in hours and minutes between CoordinatedUniversal Time (UTC) and a local time for a particular place and date.

Within the context of the present disclosure, the term, “Juliancalendar,” means the calendar set in place as the law of the land byJulius Caesar in 46 BC. The Julian calendar set the number of days in ayear at 365, except for leap years which have 366, and occurred every 4years. Pope Gregory XIII reformed the Julian calendar into the Gregoriancalendar, which further refined leap years and corrected for past errorsby skipping 10 days in October of 1582.

The smart streetlight controller 120 includes a location/identificationmodule 170. Once the smart streetlight controller 120 is deployed, thelocation/identification module 170 may be accessed to receive,calculate, generate or otherwise isolate a specific terrestrial positionof the smart streetlight controller 120. In at least some cases, thespecific terrestrial position includes a first value representing alatitude and a second value representing a longitude.

The smart streetlight controller 120 is a real time device. That is, atany given time, the smart streetlight controller 120 may retrieve,receive, calculate, generate, or otherwise isolate a specific date and aspecific time. In some cases, time and date values are parsed from datareceived by the location/identification module 170. In these or othercases, time and date values are parsed from data received by thecommunications module 164 (e.g., a transceiver arranged forcommunications according to a cellular-based protocol). In these orstill other cases, time and date values are retrieved from othercircuitry 172, which may include a real-time clock circuit. Other meansof isolating a time value and a date value are contemplated.

The smart streetlight controller 120 is configured to calculate one ormore positions of the sun relative to the terrestrial position of thesmart streetlight controller 120. Accordingly, the smart streetlightcontroller 120 may be arranged to calculate any number of desirablesolar time values. For example, considering the specific terrestriallocation of the smart streetlight controller 120, a time of sunrise atthat terrestrial location may be calculated, a time of civil dawn atthat terrestrial location may be calculated, a time of sunset at thatterrestrial location may be calculated, a time of civil dusk at thatterrestrial location may be calculated, a time when the sun is at a zerodegrees (0°) zenith angle at that terrestrial location may becalculated, or any other time associated with a specific position of thesun relative to the terrestrial position of the smart streetlightcontroller 120 may be calculated. More specifically, in at least someembodiments, the memory 180 may include at least one algorithmic module190 a that calculates specific local time values when the sun will be ina specific position. Inputs and outputs to the algorithmic module 190 amay be of any suitable form and reference system. At least one exemplaryset of operations of the algorithmic module 190 a is set forth in FIG.4A.

The memory 180 may optionally be arranged with other functional modules.For example, in some cases, the memory 180 includes an offsets module190 b, a queries module 190 c, and an other functions module 190 c.

The offsets module 190 b is arranged to generated, apply, or generatedand apply offsets to a streetlight control time. Applying such offsetsmay create one or more new or additional streetlight control times. Inmany cases, the offset is applied (e.g., added, subtracted) to acalculated time when the sun is in a particular position relative to aterrestrial position. For example, if a user of the smart streetlightcontroller 120 desires to always set at streetlight control time thatturns on a streetlight at 15 minutes before sunset, the user can store a15 minute time value offset in memory 180 and command the offsets module190 b to apply the offset to a previously or later calculatedstreetlight control time. In this way, the algorithmic module 190 a willcalculate a time of sunset on any certain day (e.g., a first streetlightcontrol time), and the offsets module 190 b will adjust the time ofsunset value by subtracting 15 minutes to create a new streetlightcontrol time (e.g., a second streetlight control time). Accordingly, thesubject streetlight will turn on at a different time each day, but thetime that the streetlight turns on will always be 15 minutes beforesunset. This functionality adds predictability, improves safety, andprovides energy efficiency that heretofore was unavailable.

One of skill in the art will recognize that any suitable number ofoffsets may be created and applied to any suitable number of streetlightcontrol times, and an offset may be optionally provided to any generatedtime value that is based on the position of the sun. The offsets may bezero or some other number. An offset may in some cases subtract time(e.g., make earlier) from a particular time value. An offset may in somecases add time to a streetlight control time, which renders a laterpoint in time. An offset may in some cases subtract time from astreetlight control time, which renders an earlier point in time.Offsets may be entered manually, programmatically, on a schedule, or inany other way.

The queries module 190 c is an optional module arranged to inquire,retrieve, and gather additional data to direct the operations of a smartstreetlight controller 120. For example, the queries module 190 c may beused to provide offsets to any generated streetlight control time thatis based on the position of the sun. The queries module 190 c maycooperate with the offsets module 190 b, the algorithmic module 190 a,or other modules of the smart streetlight controller 120.

In one case, the queries module 190 c works cooperatively with acommunications module 164. For example, the queries module 190 c mayretrieve information from a website, a network-accessible repository, aremote computing device, a local mobile computing device, or some otherinformation source. In one optional case, the queries module 190 caccesses a weather-related database or other source of weatherinformation. Based on the access to weather-related information, if itis determined that inclement weather, which will darken an areaproximate the smart streetlight controller 120, is coming, the queriesmodule 190 c may provide a weather-related offset to the offsets module190 b, which will further adjust a streetlight control time.

FIG. 4A is a data flow 400 diagram representing processing of analgorithmic module 190 a that calculates time values based on acalculated position of the sun relative to a specific terrestrialposition on Earth. The specific terrestrial position is the position(e.g., latitude, longitude) on the face of Earth of the smartstreetlight controller 120 that is executing the algorithm.

In at least one exemplary case, the data flow 400 implements a knownalgorithm in a new way. Particularly, the algorithm used as basis forthe design of at least one embodiment of executable softwareinstructions stored in a memory 180 and configured in an algorithmicmodule 190 a may be found in the ALMANAC FOR COMPUTERS, 1990, PUBLISHEDBY THE NAUTICAL ALMANAC OFFICE, U.S. NAVAL OBSERVATORY, WASHINGTON,D.C., 20392.

It is recognized that the present data flow 400 calculates the positionof the sun relative to a specific terrestrial position on Earth. Varioustime values are also generated based on the calculated position. Whilethe present data flow 400 is directed toward calculating data associatedwith the sun, one of skill in the art will recognize that the data flowis not so limited. In at least some cases, for example, a data flowalong the lines of data flow 400 (FIG. 4A) may be used to calculate theposition of the moon relative to a specific terrestrial position onEarth along with a phase of the moon as evident at the specificterrestrial position on Earth on the appointed day. In at least somecases, for example, the presence of a full moon may be used to adjust astreetlight control time. Such knowledge may also, in some cases, becoupled with local weather information isolated by the queries module190 c to adjust a streetlight control time or other illumination signalinformation that controls the light output of a particular streetlight.

Processing begins at 402 and advances to 404. At 404, a day of the yearis calculated as an offset from January 1. In some cases, the offset ismathematically calculated. In some cases, the offset is retrieved from atable of stored offsets. In some cases, the offset is retrieved from anetwork source, such as a known website. Processing advances to 406.

At 406, the longitude value of the specific terrestrial position isconverted to an hour value, and one or more approximate times arecalculated. For example, in some cases, a sunrise time is desired. Inthese or other cases, a sunset time is desired. The world is dividedinto twenty-four equally sized longitudinal time zones. Accordingly, aterrestrial position that includes longitude can be used to determine anoffset within the particular time zone. Additionally, sunrise values,sunset values, or any other values may be calculated as “hour values.”Processing advances to 408.

At 408, the sun's mean anomaly may be calculated for each desiredlongitudinal time value. The mean anomaly is the fraction of Earth'selliptical orbit period that has elapsed since Earth passed thepericenter of the orbit. Stated differently, the mean anomaly is anoffset from where Earth would be if traveling in a uniform, circularorbit rather than an elliptical orbit. In at least some cases, the meananomaly is calculated as an angular offset or angular distance from thepericenter that Earth would have if it had been moving in a circularorbit, with constant speed, in the same orbital period as the Earthactually travels in its non-circular (i.e., elliptical) orbit.Processing advances to 410.

At 410, the sun's true longitude is calculated as a trigonometricfunction of the mean anomaly. The sun's true longitude is relative tothe terrestrial position of the specific smart streetlight controller120 that is executing the algorithm. Processing advances to 412.

At 412, the right ascension of the sun is calculated and converted to atime value such as hours. In these cases, the time value is a realnumber stored, for example, as a floating-point number, which may haveany suitable precision. A first right ascension value is generated astrigonometric function of the sun's longitude. If necessary, the firstcalculated value is offset or otherwise adjusted to reflect a value inthe same longitudinal quadrant as the terrestrial position of thespecific smart streetlight controller 120 that is executing thealgorithm. And finally, the right ascension value is converted into atime value (e.g., hours). The sun's ascension value may be thought of asan indication of where the sun is on an east-west trajectory relative tothe terrestrial position. Processing advances to 414.

At 414, the sun's declination is calculated as a trigonometric functionof the sun's longitude. The sun's declination may be thought of as anindication of how high the sun is in the sky relative the terrestrialposition. Processing advances to 416.

At 416, the sun's local hour angle is calculated and converted to a timevalue (e.g., hours). The local hour angle may be calculated as atrigonometric function based on the sun's zenith and the latitudinalposition of the specific smart streetlight controller 120 that isexecuting the algorithm. Subsequently, the local hour angle istranslated to a desirable time value (e.g., hours). Processing advancesto 418.

At 418, the time value of the local solar hour angle is used tocalculate mean time values of any point on the apparent solartrajectory. For example, a mean sunrise time may be calculated, a meansunset time may be calculated, or any other such time. The mean timevalues are calculated as a function of the calculate right ascension andthe local hour angle. Processing advances to 420.

At 420, the calculated mean time values are adjusted to CoordinatedUniversal Time (UTC), and optionally further converted to the local timeat the terrestrial position of the specific smart streetlight controller120 that is executing the algorithm.

Processing advances to 422 and terminates.

FIG. 4B is a data flow 450 diagram representing processing of a smartstreetlight controller 120 to generate one or more streetlight controltimes and any suitable illumination signal information.

Processing begins at 452 and advances to 454. At 454, a terrestrialposition of a smart streetlight controller is isolated. In some cases,the specific terrestrial position is provided by alocation/identification module 170. The terrestrial position may includelatitude and longitude, a street address, a legal description from a taxassessor, or some other location information. In some cases, a devicesuch as a global positioning system (GPS) is used to generate a specificterrestrial position. In some cases, the specific terrestrial positionis hard coded in a memory such as memory 180 or hard coded in a modulesuch as the location/identification module 170. In some cases, thespecific terrestrial position is programmatically received and stored inmemory.

Also at 454, a specific date, a plurality of dates, or range of dates isisolated. The date or dates are used to calculate a date certain, a timecertain, or a date and time certain when a position of a celestial bodysuch as the sun will be determined relative to one or more specificterrestrial positions. Processing advances to 456.

At 456, an algorithm module 190 a is invoked to calculate, at the smartstreetlight controller 120, a time value associated with an eventdefined by a position of a celestial body such as the sun or moon on thespecific date or dates. The time value that is calculated may be any oneor more of sunrise, sunset, civil dawn, civil dusk, high-noon, or someother time value. Processing in the algorithm module may be along thelines of the data flow 400 of FIG. 4A. In cases where a position of themoon is determined, a phase of the moon may also be determined. In somecases, a position and phase of the moon is used to generate or adjust astreetlight control time or to generate certain illumination signalinformation. Processing advances to 458.

At 458, based on the time value or values calculated at 456, one or morestreetlight control times may be generated. As discussed herein, astreetlight control time is a time (e.g., a real-time value, a relativetime value, a time offset from another time value, a prioritized timevalue, a conditional time value, or some other time value) at which astreetlight or one of its functions (e.g., illumination signalinformation) may be controlled.

In some cases, controlling a streetlight based on a streetlight controltime includes communicating certain illumination signal information. Theillumination signal information may include any such analog or digitalsignaling that directs or otherwise causes a light source to turn on,turn off, dim, dim to a specific light output, flash, flash a code or anencoded message, change the properties of generated light (e.g., color,intensity, warmth, and the like), or control the streetlight in anyother way. The operations of the light source may be enabled, performed,directed, or otherwise implemented via a PWM module 174, a DALIcontroller module 176, a DALI power supply 178, or some other mechanism(e.g., I/O module 166, other functions module 190 d, a reset module 168,a certain software function stored in code 182, or the light sourcecontrol may be implemented in some other way. In these or still othercases, a streetlight control time may be used to direct another functionsuch as taking a photograph, recording audio, communicating a message toa remote computer or mobile device or some other computing device, ordirecting some other action. Processing advances to 460.

At 460, one or more offsets to a streetlight control time are generatedand applied to create one or more updated streetlight control times. Theoffsets may be a specific time before sunrise, after sunrise, beforesunset, after sunset, or some other offset. In some cases, an offset iszero; in other cases, the offset is a negative value. Offsets may be indays, hours, minutes, seconds, or some other unit of time. In somecases, offsets may be conditional. For example, an offset may be a firstvalue during a winter season and a second value during a summer season.Seasonal offsets may be further conditional on the specific terrestrialposition of the smart streetlight controller 120. Processing advances to462. At 462, any suitable number of zero or more queries are performedto gather additional information that may affect one or more streetlightcontrol times. The queries may be managed or otherwise implemented by orthrough a queries module 190 c. The queries may cover a wide variety oftopics, features, sensors, circuits, and the like. A query that affectsa streetlight control time may retrieve information from a sensorintegrated with, or coupled to, the smart streetlight controller 120. Aquery that affects a streetlight control time may retrieve informationfrom a network-accessible source such as website, a government agency, aprivate commercial database, a public commercial database, a library, amobile device, a manually entered datum, or any other such source. Theinformation captured may be used to adjust, overwrite, or affect astreetlight control time in any suitable way. Processing advances to464.

At 464, one or more streetlight control times are used to direct aparticular action of a smart streetlight controller 120 such as a lightsource of a streetlight. In addition, one or more functions of astreetlight associated with the smart streetlight controller 120 mayalso be controlled by modifying or otherwise generating the illuminationsignal information.

Processing advances back to 454 and continue in perpetuity.

Having now set forth certain embodiments, further clarification ofcertain terms used herein may be helpful to providing a more completeunderstanding of that which is considered inventive in the presentdisclosure.

Internet of Things (IOT) and Industrial Internet of Things (IIOT)devices are fixed and/or mobile electronic computing devices that arecoupled or coupleable to a computing network. IOT devices are oftendescribed as devices with consumer facing applicability and IIOT devicesare often described as devices with industrial or machine-to-machineapplicability. The two types of devices (i.e., IOT and IIOT devices)have one or more computing processors, memory storing instructions thatdirect operations of the one or more computing processors, and networkcircuitry. In many cases, the IOT and IIOT devices also include a powersource (e.g., one or more of a battery, a physical power interface, apower supply, a photovoltaic cell, an induction coil, etc.), at leastone sensor (e.g., accelerometer, photo sensor, thermometer, and manyothers), and memory to store data collected by the device.

The present disclosure will use the term IIOT devices, but it isrecognized that the principles described herein are equally applicableto IOT devices.

Rather than a general-purpose computing device, an IIOT device istypically arranged to perform a particular function or set of functions.An IIOT device may, for example, be arranged as an environmental sensorthat collects data such as temperature, humidity, air quality, and thelike. In these cases, the IIOT device is deployed in a city, rural area,or some other location, and the device is either programmed on site orat the factory to communicate with a specific remote computing server.The remote computing server may be arranged at a great distance (e.g.,tens, hundreds, or even thousands of miles away) from the IIOT device.Alternatively, the remote computing server may be a smart phone tablet,or other computing device permanently or transitorily arranged a shortdistance (e.g., tens or hundreds of feet or inches or some otherdistance) from the IIOT device. In these cases, the IIOT device isprogrammed to communicate data to, from, or to and from a specificremote computing server.

Mobile network operators (MNOs) provide wireless cellular-based servicesin accordance with one or more cellular-based technologies. As used inthe present disclosure, “cellular-based” should be interpreted in abroad sense to include any of the variety of technologies that implementwireless or mobile communications. Exemplary cellular-based systemsinclude, but are not limited to, time division multiple access (“TDMA”)systems, code division multiple access (“CDMA”) systems, and GlobalSystem for Mobile communications (“GSM”) systems. Some others of thesetechnologies are conventionally referred to as UMTS, WCDMA, 4G, 5G, 6G,and LTE. Still other cellular-based technologies are also known now orwill be known in the future. The underlying cellular-based technologiesare mentioned here for a clearer understanding of the presentdisclosure, but the inventive aspects discussed herein are not limitedto any particular cellular-based technology.

In some cases, cellular-based voice traffic is treated as digital data.In such cases, the term “voice-over-Internet-Protocol”, or “VoIP,” maybe used to mean any type of voice service that is provided over a datanetwork, such as an Internet Protocol (IP) based network. The term VoIPis interpreted broadly to include any system wherein a voice signal froma mobile computing device is represented as a digital signal thattravels over a data network. VoIP then may also include any systemwherein a digital signal from a data network is delivered to a mobilecomputing device where it is later delivered as an audio signal.

Standardized powerline interface connector devices of the typesdescribed herein are in at least some cases referred to as NEMA devices,NEMA compatible devices, NEMA compliant devices, or the like. And thesedevices include receptacles, connectors, sockets, holders, components,etc. Hence, as used in the present disclosure and elsewhere, those ofskill in the art will recognize that coupling the term “NEMA” or theterm “ANSI” with any such device indicates a device or structurecompliant with a standard promoted by a standards body such as NEMA,ANSI, IEEE, or the like.

A mobile device, or mobile computing device, is an electronic deviceprovisioned by at least one mobile network operator (MNO) to communicatedata through the MNO's cellular-based network. The data may be voicedata, short message service (SMS) data, electronic mail, world-wide webor other information conventionally referred to as “internet traffic,”or any other type of electromagnetically communicable information. Thedata may be digital data or analog data. The data may be packetized ornon-packetized. The data may be formed or passed at a particularpriority level, or the data may have no assigned priority level at all.A non-comprehensive, non-limiting list of mobile devices is provided toaid in understanding the bounds of the term, “mobile device,” as usedherein. Mobile devices (i.e., mobile computing devices) include cellphones, smart phones, flip phone, tablets, phablets, handheld computers,laptop computers, body-worn computers, and the like. Certain otherelectronic equipment, such as IOT devices, IIOT devices, smart devices,and other like computing devices in any form factor, may also bereferred to as a mobile device when this equipment is provisioned forcellular-based communication on an MNO's cellular-based network.Examples of this other electronic equipment include in-vehicle devices,medical devices, industrial equipment, retail sales equipment, wholesalesales equipment, utility monitoring equipment, streetlight controllers,small cells, transformer monitors, any type of “smart-city” devices, andother such equipment used by private, public, government, and otherentities.

Mobile devices further have a collection of input/output ports forpassing data over short distances to and from the mobile device. Forexample, serial ports, USB ports, WiFi ports, Bluetooth ports, IEEE 1394FireWire, and the like can communicatively couple the mobile device toother computing apparatuses.

Mobile devices have a battery or other power source, and they may or maynot have a display. In many mobile devices, a signal strength indicatoris prominently positioned on the display to provide networkcommunication connectivity information to the mobile device user.

A cellular transceiver is used to couple the mobile device to othercommunication devices through the cellular-based communication network.In some cases, software and data in a file system are communicatedbetween the mobile device and a computing server via the cellulartransceiver. That is, bidirectional communication between a mobiledevice and a global or local computing server is facilitated by thecellular transceiver. For example, a computing server may download a newor updated version of software to the mobile device over thecellular-based communication network. As another example, the mobiledevice may communicate any other data to the computing server over thecellular-based communication network.

Each mobile device client has electronic memory accessible by at leastone processing unit within the device. The memory is programmed withsoftware that directs the one or more processing units. Some of thesoftware modules in the memory control the operation of the mobiledevice with respect to generation, collection, and distribution or otheruse of data. In some cases, software directs the collection ofindividual datums, and in other cases, software directs the collectionof sets of data.

FIGS. 4A-4B are data flow diagrams illustrating non-limiting processesthat may be used by embodiments of an IIOT device such as a smartstreetlight controllers 120. In this regard, each described process mayrepresent a module, segment, or portion of software code, whichcomprises one or more executable instructions for implementing thespecified logical function(s). It should also be noted that in someimplementations, the functions noted in the process may occur in adifferent order, may include additional functions, may occurconcurrently, and/or may be omitted.

The figures in the present disclosure illustrate portions of one or morenon-limiting computing devices embodiments such as one or more smartstreetlight controllers 120. The computing devices may include operativehardware found in conventional computing device apparatuses such as oneor more processors, volatile and non-volatile memory, serial andparallel input/output (I/O) circuitry compliant with various standardsand protocols, wired and/or wireless networking circuitry (e.g., acommunications transceiver), one or more user interface (UI) modules,logic, and other electronic circuitry.

Processing devices, or “processors,” as described herein, includecentral processing units (CPU's), microcontrollers (MCU), digital signalprocessors (DSP), application specific integrated circuits (ASIC),peripheral interface controllers (PIC), state machines, and the like.Accordingly, a processor as described herein includes any device,system, or part thereof that controls at least one operation, and such adevice may be implemented in hardware, firmware, or software, or somecombination of at least two of the same. The functionality associatedwith any particular processor may be centralized or distributed, whetherlocally or remotely. Processors may interchangeably refer to any type ofelectronic control circuitry configured to execute programmed softwareinstructions. The programmed instructions may be high-level softwareinstructions, compiled software instructions, assembly-language softwareinstructions, object code, binary code, micro-code, or the like. Theprogrammed instructions may reside in internal or external memory or maybe hard-coded as a state machine or set of control signals. According tomethods and devices referenced herein, one or more embodiments describesoftware executable by the processor, which when executed, carries outone or more of the method acts.

The present application discusses several embodiments of industrialinternet of things (IIOT) devices (e.g., smart streetlight controllers120) that include or otherwise cooperate with one or more computingdevices. It is recognized that these IIOT devices are arranged toperform one or more algorithms to implement various concepts taughtherein. Each of said algorithms is understood to be a finite sequence ofsteps for solving a logical or mathematical problem or performing atask. Any or all of the algorithms taught in the present disclosure maybe demonstrated by formulas, flow charts, data flow diagrams, narrativesin the specification, and other such means as evident in the presentdisclosure. Along these lines, the structures to carry out thealgorithms disclosed herein include at least one processing deviceexecuting at least one software instruction retrieved from at least onememory device. The structures may, as the case may be, further includesuitable input circuits known to one of skill in the art (e.g.,keyboards, buttons, memory devices, communication circuits, touch screeninputs, and any other integrated and peripheral circuit inputs (e.g.,accelerometers, thermometers, light detection circuits and other suchsensors)), suitable output circuits known to one of skill in the art(e.g., displays, light sources, audio devices, tactile devices, controlsignals, switches, relays, and the like), and any additional circuits orother structures taught in the present disclosure. To this end, everyinvocation of means or step plus function elements in any of the claims,if so desired, will be expressly recited.

As known by one skilled in the art, smart streetlight controllers 120have one or more memories, and each memory comprises any combination ofvolatile and non-volatile computer-readable media for reading andwriting. Volatile computer-readable media includes, for example, randomaccess memory (RAM). Non-volatile computer-readable media includes, forexample, read only memory (ROM), magnetic media such as a hard-disk, anoptical disk, a flash memory device, a CD-ROM, and/or the like. In somecases, a particular memory is separated virtually or physically intoseparate areas, such as a first memory, a second memory, a third memory,etc. In these cases, it is understood that the different divisions ofmemory may be in different devices or embodied in a single memory. Thememory in some cases is a non-transitory computer medium configured tostore software instructions arranged to be executed by a processor. Someor all of the stored contents of a memory may include softwareinstructions executable by a processing device to carry out one or moreparticular acts.

The smart streetlight controllers 120 illustrated herein may furtherinclude operative software found in a conventional computing device suchas an operating system or task loop, software drivers to directoperations through I/O circuitry, networking circuitry, and otherperipheral component circuitry. In addition, the computing devices mayinclude operative application software such as network software forcommunicating with other computing devices, database software forbuilding and maintaining databases, and task management software whereappropriate for distributing the communication and/or operationalworkload amongst various processors. In some cases, the smartstreetlight controllers 120 is a single hardware machine having at leastsome of the hardware and software listed herein, and in other cases, thesmart streetlight controllers 120 embodiments are a networked collectionof hardware and software machines working together cooperatively in aserver farm, cluster, cloud, or other networked environment to executethe functions of one or more embodiments described herein. Some aspectsof the conventional hardware and software of the particular computingdevice are not shown in the figures for simplicity.

Amongst other things, the exemplary computing devices of the presentdisclosure (e.g., smart streetlight controllers 120 of FIGS. 2-3 ) maybe configured in any type of mobile or stationary computing device suchas a remote cloud computer, a computing server, a smartphone, a tablet,a laptop computer, a wearable device (e.g., eyeglasses, jacket, shirt,pants, socks, shoes, other clothing, hat, helmet, other headwear,wristwatch, bracelet, pendant, other jewelry), vehicle-mounted device(e.g., train, plane, helicopter, unmanned aerial vehicle, unmannedunderwater vehicle, unmanned land-based vehicle, automobile, motorcycle,bicycle, scooter, hover-board, other personal or commercialtransportation device), industrial device (e.g., factory robotic device,home-use robotic device, retail robotic device, office-environmentrobotic device), or the like. Accordingly, the computing devices includeother components and circuitry that is not illustrated, such as, forexample, a display, a network interface, memory, one or more centralprocessors, camera interfaces, audio interfaces, and other input/outputinterfaces. In some cases, the exemplary computing devices may also beconfigured in a different type of low-power device such as a mountedvideo camera, an Internet-of-Things (IoT) device, a multimedia device, amotion detection device, an intruder detection device, a securitydevice, a crowd monitoring device, or some other device.

When so arranged as described herein, each IIOT device may betransformed from a generic and unspecific computing device to acombination device arranged comprising hardware and software configuredfor a specific and particular purpose such as to provide a determinedtechnical solution. When so arranged as described herein, to the extentthat any of the inventive concepts described herein are found by a bodyof competent adjudication to be subsumed in an abstract idea, theordered combination of elements and limitations are expressly presentedto provide a requisite inventive concept by transforming the abstractidea into a tangible and concrete practical application of that abstractidea.

The embodiments described herein use computerized technology to improvethe technology of smart streetlight controllers and otherprocessor-based “smart” devices, but other techniques and tools remainavailable to provision said IIOT devices and other smart devices.Therefore, the claimed subject matter does not foreclose the whole oreven substantial streetlight controller technical field. The innovationdescribed herein uses both new and known building blocks combined in newand useful ways along with other structures and limitations to createsomething more than has heretofore been conventionally known. Theembodiments improve on computing systems which, when un-programmed ordifferently programmed, cannot perform or provide the specificstreetlight control features that include onboard calculation of theposition of the sun relative to a terrestrial position of the smartstreetlight controller on any given day as taught herein. Theembodiments described in the present disclosure improve upon knownstreetlight controller processes and techniques. The computerized actsdescribed in the embodiments herein are not purely conventional and arenot well understood. Instead, the acts are new to the industry.Furthermore, the combination of acts as described in conjunction withthe present embodiments provides new information, motivation, andbusiness results that are not already present when the acts areconsidered separately. There is no prevailing, accepted definition forwhat constitutes an abstract idea. To the extent the concepts discussedin the present disclosure may be considered abstract, the claims presentsignificantly more tangible, practical, and concrete applications ofsaid allegedly abstract concepts. And said claims also improvepreviously known computer-based systems that perform streetlightcontroller functions and other smart computing device operations.

Software may include a fully executable software program, a simpleconfiguration data file, a link to additional directions, or anycombination of known software types. When a computing device updatessoftware, the update may be small or large. For example, in some cases,a computing device downloads a small configuration data file to as partof software, and in other cases, a computing device completely replacesmost or all of the present software on itself or another computingdevice with a fresh version. In some cases, software, data, or softwareand data is encrypted, encoded, and/or otherwise compressed for reasonsthat include security, privacy, data transfer speed, data cost, or thelike.

Repositories (e.g., database structures), if any are present in the IIOTand other computing systems described herein, may be formed in a singlerepository or multiple repositories. In some cases hardware or softwarestorage repositories are shared amongst various functions of theparticular system or systems to which they are associated. A repository(e.g., database) may be formed as part of a local system or local areanetwork. Alternatively, or in addition, a repository may be formedremotely, such as within a distributed “cloud” computing system, whichwould be accessible via a wide area network or some other network.

Input/output (I/O) circuitry and user interface (UI) modules includeserial ports, parallel ports, universal serial bus (USB) ports, IEEE802.11 transceivers and other transceivers compliant with protocolsadministered by one or more standard-setting bodies, displays,projectors, printers, keyboards, computer mice, microphones,micro-electro-mechanical (MEMS) devices such as accelerometers, and thelike.

In at least one embodiment, devices such as the smart streetlightcontrollers 120 may communicate with other devices via communicationover a network. The network may involve an Internet connection or someother type of local area network (LAN) or wide area network (WAN).Non-limiting examples of structures that enable or form parts of anetwork include, but are not limited to, an Ethernet, twisted pairEthernet, digital subscriber loop (DSL) devices, wireless LAN, Wi-Fi,Worldwide Interoperability for Microwave Access (WiMax), or the like.

In the present disclosure, memory may be used in one configuration oranother. The memory may be configured to store data. In the alternativeor in addition, the memory may be a non-transitory computer readablemedium (CRM). The CRM is configured to store computing instructionsexecutable by a processor of the smart streetlight controller 120 andcomputing servers 250, 250 a, 250 b, 550 c, and 550 f. The computinginstructions may be stored individually or as groups of instructions infiles. The files may include functions, services, libraries, and thelike. The files may include one or more computer programs or may be partof a larger computer program. Alternatively or in addition, each filemay include data or other computational support material useful to carryout the computing functions of an IIOT device or some other computingsystem.

Buttons, keypads, computer mice, memory cards, serial ports, bio-sensorreaders, touch screens, and the like may individually or in cooperationbe useful to a technician operating an IIOT device or other computingsystem. The devices may, for example, input control information into thesystem. Displays, printers, memory cards, LED indicators, temperaturesensors, audio devices (e.g., speakers, piezo device, etc.), vibrators,and the like are all useful to present output information to thetechnician operating the IIOT device or other computing system. In somecases, the input and output devices are directly coupled to the smartstreetlight controllers 120 and computing servers 250, 250 a, 250 b, 550c, and 550 f and electronically coupled to a processor or otheroperative circuitry. In other cases, the input and output devices passinformation via one or more communication ports (e.g., RS-232, RS-485,infrared, USB, etc.).

As described herein, for simplicity, a technician may in some cases bedescribed in the context of the male gender. It is understood that atechnician can be of any gender, and the terms “he,” “his,” and the likeas used herein are to be interpreted broadly inclusive of all knowngender definitions. As the context may require in this disclosure,except as the context may dictate otherwise, the singular shall mean theplural and vice versa; all pronouns shall mean and include the person,entity, firm or corporation to which they relate; and the masculineshall mean the feminine and vice versa.

As used in the present disclosure, the term “module” refers to anapplication specific integrated circuit (ASIC), an electronic circuit, aprocessor and a memory operative to execute one or more software orfirmware programs, combinational logic circuitry, or other suitablecomponents (hardware, software, or hardware and software) that providethe functionality described with respect to the module.

The terms, “real-time” or “real time,” as used herein and in the claimsthat follow, are not intended to imply instantaneous processing,transmission, reception, or otherwise as the case may be. Instead, theterms, “real-time” and “real time” imply that the activity occurs overan acceptably short period of time (e.g., over a period of microsecondsor milliseconds), and that the activity may be performed on an ongoingbasis (e.g., inputting system-wide unique identifiers (SWUI'S) of aplurality of IOT devices, IIOT devices, or other smart computingdevices, inputting batch ID's, receiving information from the particularcomputing device, and the like). An example of an activity that is notreal-time is one that occurs over an extended period of time (e.g.,days, months, or years for a single instance) or that occurs based onintervention or direction by a technician or other activity.

In the absence of any specific clarification related to its express usein a particular context, where the terms “substantial” or “about” in anygrammatical form are used as modifiers in the present disclosure and anyappended claims (e.g., to modify a structure, a dimension, ameasurement, or some other characteristic), it is understood that thecharacteristic may vary by up to 30 percent. For example, a small cellnetworking device may be described as being mounted “substantiallyhorizontal,” In these cases, a device that is mounted exactly horizontalis mounted along an “X” axis and a “Y” axis that is normal (i.e., 90degrees or at right angle) to a plane or line formed by a “Z” axis.Different from the exact precision of the term, “horizontal,” and theuse of “substantially” or “about” to modify the characteristic permits avariance of the particular characteristic by up to 30 percent. Asanother example, a small cell networking device having a particularlinear dimension of between about six (6) inches and twelve (12) inchesincludes such devices in which the linear dimension varies by up to 30percent. Accordingly, the particular linear dimension of the small cellnetworking device may be between 2.4 inches and 15.6 inches.

Where a range of values is provided, it is understood that eachintervening value, to the tenth of the unit of the lower limit unlessthe context clearly dictates otherwise, between the upper and lowerlimit of that range and any other stated or intervening value in thatstated range is encompassed within the invention. The upper and lowerlimits of these smaller ranges may independently be included in thesmaller ranges is also encompassed within the invention, subject to anyspecifically excluded limit in the stated range. Where the stated rangeincludes one or both of the limits, ranges excluding either or both ofthose included limits are also included in the invention.

Unless defined otherwise, the technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this invention belongs. Although any methods andmaterials similar or equivalent to those described herein can also beused in the practice or testing of the present invention, a limitednumber of the exemplary methods and materials are described herein.

In the present disclosure, when an element (e.g., component, circuit,device, apparatus, structure, layer, material, or the like) is referredto as being “on,” “coupled to,” or “connected to” another element, theelements can be directly on, directly coupled to, or directly connectedto each other, or intervening elements may be present. In contrast, whenan element is referred to as being “directly on,” “directly coupled to,”or “directly connected to” another element, there are no interveningelements present.

The terms “include” and “comprise” as well as derivatives and variationsthereof, in all of their syntactic contexts, are to be construed withoutlimitation in an open, inclusive sense, (e.g., “including, but notlimited to”). The term “or,” is inclusive, meaning and/or. The phrases“associated with” and “associated therewith,” as well as derivativesthereof, can be understood as meaning to include, be included within,interconnect with, contain, be contained within, connect to or with,couple to or with, be communicable with, cooperate with, interleave,juxtapose, be proximate to, be bound to or with, have, have a propertyof, or the like.

Reference throughout this specification to “one embodiment” or “anembodiment” and variations thereof means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, the appearances of thephrases “in one embodiment” or “in an embodiment” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

In the present disclosure, the terms first, second, etc., may be used todescribe various elements, however, these elements are not be limited bythese terms unless the context clearly requires such limitation. Theseterms are only used to distinguish one element from another. Forexample, a first machine could be termed a second machine, and,similarly, a second machine could be termed a first machine, withoutdeparting from the scope of the inventive concept.

As used in this specification and the appended claims, the singularforms “a,” “an,” and “the” include plural referents unless the contentand context clearly dictates otherwise. It should also be noted that theconjunctive terms, “and” and “or” are generally employed in the broadestsense to include “and/or” unless the content and context clearlydictates inclusivity or exclusivity as the case may be. In addition, thecomposition of “and” and “or” when recited herein as “and/or” isintended to encompass an embodiment that includes all of the associateditems or ideas and one or more other alternative embodiments thatinclude fewer than all of the associated items or ideas.

In the present disclosure, conjunctive lists make use of a comma, whichmay be known as an Oxford comma, a Harvard comma, a serial comma, oranother like term. Such lists are intended to connect words, clauses orsentences such that the thing following the comma is also included inthe list.

The use of the phrase “set” (e.g., “a set of items”) or “subset,” unlessotherwise noted or contradicted by context, is to be construed as anonempty collection comprising one or more members.

The headings and Abstract of the Disclosure provided herein are forconvenience only and do not interpret the scope or meaning of theembodiments.

In at least one example, a plurality of hundreds of IIOT devices aresold to a particular city. In this case, the IIOT devices arestreetlight controllers, and each of the hundreds of streetlightcontrollers, along with thousands, tens of thousands, hundreds ofthousands, or some other number of streetlight controllers areprogrammed at a factory with identical network communication parameters.When any of the hundreds, thousands, or millions of streetlightcontrollers are deployed, the streetlight controller will firstcommunicate with a same global remote computing server. In this firstcommunication, based on a system-wide unique identifier of theparticular streetlight controller, the global remote computing serverwill determine which customer (e.g., city, power utility, department oftransportation, or the like) the streetlight controller belongs to.Next, the global remote computing server will return a network addressof a customer-based computing server that the streetlight controllershould communicate with. In the example, this process is carried out bythe city's hundreds of streetlight controllers, and each of thosestreetlight controllers will reprogram itself with the new networkaddress. In this way, the city's customer-based computing server will beable to manage the hundreds of streetlight controllers, for example, bydisplaying a map, overlaying a location of each streetlight controlleron the map, and populating the map or other such content withinformation about each streetlight or its associated streetlightcontroller.

The various embodiments described above can be combined to providefurther embodiments. Various features of the embodiments are optional,and, features of one embodiment may be suitably combined with otherembodiments. Aspects of the embodiments can be modified, if necessary toemploy concepts of the various patents, application and publications toprovide yet further embodiments.

The celestial scheduling technology described in the present disclosureprovide several technical effects and advances to the field ofstreetlight controllers.

Technical effects and benefits include the ability to improve thereliability, energy efficiency, and safety of streetlighting.Conventional streetlight controllers include photo-sensitive circuitry(e.g., a photosensor) to determine when the streetlight should turn onand when the streetlight should turn off. If the photosensor circuitfails, or if a window to the sensor is obstructed (e.g., by dirt, fowl,damage, or some other cause), the streetlight may either be wastefullyalways illuminated or dangerously always extinguished. In the presentdisclosure, a programmatic approach to overcome the limitations ofconventional streetlight controllers is proposed. The new approach maybe used cooperatively with photo-sensitive circuitry or as analternative to photo-sensitive circuitry. What's more, with a determinedlevel of expected ambient light, the streetlight controller may finelytune a streetlight to illuminate more brightly or less brightly in adesired way. This improvement can increase safety, save energy, andprovide a more uniform illumination over the course of a single eveningor a climatic season.

The present disclosure sets forth details of various structuralembodiments that may be arranged to carry the teaching of the presentdisclosure. By taking advantage of the flexible circuitry, mechanicalstructures, computing architecture, and communications means describedherein, a number of exemplary devices and systems are now disclosed.

Example A-1 teaches A method to control a streetlight with a smartstreetlight controller, comprising: isolating a terrestrial position ofthe smart streetlight controller; isolating a specific date;calculating, at the smart streetlight controller, a time valueassociated with an event defined by a position of the sun on thespecific date; generating a streetlight control time by applying anoffset to the time value; and executing a streetlight control command atthe streetlight control time.

Example A-1 may include the subject matter of Example A-1, andalternatively or additionally any other example herein, wherein thestreetlight control command is a command to turn on the streetlight.

These and other changes can be made to the embodiments in light of theabove-detailed description. In general, in the following claims, theterms used should not be construed to limit the claims to the specificembodiments disclosed in the specification and the claims, but should beconstrued to include all possible embodiments along with the full scopeof equivalents to which such claims are entitled. Accordingly, theclaims are not limited by the disclosure.

Various devices that utilize the circuits and modules of the presentdisclosure are described in U.S. Patent Application No. 62/614,918,filed Jan. 8, 2018, which is incorporated herein by reference in itsentirety to the fullest extent allowed by law.

Various devices that utilize the circuits and modules of the presentdisclosure are described in International Patent ApplicationPCT/US2019/012775, filed Jan. 8, 2019, which is incorporated byreference in its entirety to the fullest extent allowed by law.

U.S. Provisional Patent Application No. 63/002,190, filed Mar. 30, 2020,is incorporated herein by reference, in its entirety.

These and other changes can be made to the embodiments in light of theabove-detailed description. In general, in the following claims, theterms used should not be construed to limit the claims to the specificembodiments disclosed in the specification and the claims, but should beconstrued to include all possible embodiments along with the full scopeof equivalents to which such claims are entitled. Accordingly, theclaims are not limited by the disclosure.

The invention claimed is:
 1. A luminaire-mountable streetlightcontroller comprising: a powerline interface having primary contactsarranged to receive a plurality of power transmission signals from aluminaire connector to which the primary contacts areelectromechanically coupled and secondary contacts arranged tocommunicate illumination commands to a controllable light source of aluminaire; a location positioning device; a processor arranged toreceive terrestrial position information from the location positioningdevice; and a memory coupled to the processor, the memory storinginstructions which, when executed by the processor, cause the processorto: isolate, via the terrestrial position information, a terrestrialposition of the location positioning device; isolate a specific date;calculate a time value associated with an event defined by a position ofthe sun on the specific date at the terrestrial position; generate astreetlight control time by applying an offset to the time value; andcause the illumination command to be presented to the secondary contactsat the streetlight control time.
 2. The streetlight controller of claim1, wherein one or more of the illumination commands directs thecontrollable light source to flash.
 3. The streetlight controller ofclaim 1, wherein the location positioning device includes a globalpositioning system (GPS) device, and the terrestrial position includes alatitude value and a longitude value.
 4. The streetlight controller ofclaim 1, wherein one or more of the illumination commands directs thecontrollable light source to either turn on or turn off.
 5. Thestreetlight controller of claim 1, wherein the illumination commandsdirects the controllable light source to dim to a specific light output.6. The streetlight controller of claim 1, wherein the specific date isderived from the terrestrial position information.
 7. A streetlightsystem comprising: a streetlight support structure; a luminairesupported by the streetlight support structure and including acontrollable light source and a socket connector located on a top sideof the luminaire; a streetlight controller electromechanically coupledto the luminaire, the streetlight controller including: primary contactsinserted into the socket connector of the luminaire, the primarycontacts receiving power signals from the luminaire, secondary contactsarranged to communicate streetlight control commands to controllablelight source, a location positioning device; a processor arranged toreceive terrestrial position information from the location positioningdevice; and a memory coupled to the processor, the memory storinginstructions which, when executed by the processor, cause the processorto: isolate, via the terrestrial position information, a terrestrialposition of the location positioning device; isolate a specific date;calculate a time value associated with an event defined by a position ofthe sun on the specific date at the terrestrial position; generate astreetlight control time by applying an offset to the time value; andcause the streetlight control commands to be presented to the secondarycontacts at the streetlight control time.
 8. The streetlight system ofclaim 7, wherein one or more of the streetlight control commands directsthe controllable light source to flash.
 9. The streetlight system ofclaim 7, wherein the location positioning device includes a globalpositioning system (GPS) device, and the terrestrial position includes alatitude value and a longitude value.
 10. The streetlight system ofclaim 7, wherein one or more of the streetlight control commands directsthe controllable light source to either turn on or turn off.
 11. Thestreetlight system of claim 7, wherein one or more of the streetlightcontrol commands directs the controllable light source to dim to aspecific light output.
 12. The streetlight system of claim 7, whereinthe specific date is derived from the terrestrial position information.